home *** CD-ROM | disk | FTP | other *** search
- Path: news1.h1.usa.pipeline.com!usenet
- From: grantp@usa.pipeline.com(Pete)
- Newsgroups: comp.lang.c++
- Subject: Re: Newbie Question : Borland Turbo C++ V.3
- Date: 23 Feb 1996 11:50:24 GMT
- Organization: Kalevi, Inc.
- Message-ID: <4gk9m0$336@news1.usa.pipeline.com>
- NNTP-Posting-Host: pipe8.h1.usa.pipeline.com
- X-PipeUser: grantp
- X-PipeHub: usa.pipeline.com
- X-PipeGCOS: (Pete)
- X-Newsreader: Pipeline USA v3.3.0
-
- On Feb 22, 1996 12:08:41 in article <Newbie Question : Borland Turbo C++
- V.3>, 'Martyn Read <Martyn@csmltd.demon.co.uk>' wrote:
-
-
- >Hello everybody,
- >I wonder if someone can help me?
- >I want to create my own libraries and, despite much reading of the
- >manual I have been unable to work out how to do it.
- >If there is a manual entry please point me to it, if not perhaps someone
- >would be kind enough to tell me if it can be done and how to do it.
- >
- >Many thanks in advance,
- >I don't subscribe to this group normally so a direct reply would be
- >appreciated.
- >
- 1. Create a header file with all the exported function
- declarations (prototypes).
-
- 2. Create one or more source files that contain the definitions
- for the functions declared in the header. Also define internal
- library functions and whatever else you need.
-
- 3. Create a project (I'm not a TC user so I don't know the
- exact steps, but in BC it's Project | New). Choose the
- option that designates your project as a static library.
-
- 4. Add the file(s) in step 2 to your project.
-
- 5. Shift-F9 (I believe) to compile and create a library.
-
- Voila! You now have a file .lib that you can link to any
- compatible calling project. Don't forget to #include
- the library header file (Step 1) in all source code files
- that call any of the library functions.
-
- --
- Pete Grant
- Kalevi, Inc.
- Software Engineering & development
-